feat(qov-2294): Handle ACCESS_DENIED audit log - #3018

Summary

Issue: https://qovery.atlassian.net/browse/QOV-2294

Handle Access Denied audit log type

Screenshots / Recordings

Testing

• Changes tested locally in the relevant Console's pages and Storybooks
• yarn test or yarn test -u (if you need to regenerate snapshots)
• yarn format
• yarn lint

PR Checklist

• I followed naming, styling, and TypeScript rules (see .cursor/rules)
• I performed a self-review (diff inspected, dead code removed)
• I titled the PR using Conventional Commits with a scope when possible (e.g. feat(service): add new Terraform service) - required for semantic-release
• I only kept necessary comments, written in English (watch for useless AI comments)
• I involved a designer to validate UI changes if I am not a designer
• I covered new business logic with tests (unit)
• I confirmed CI is green (Codecov red can be accepted)
• I reviewed and executed locally any AI-assisted code

Summary by cubic

Marks ACCESS_DENIED audit log events as failed so they render with the red failure tag instead of appearing neutral.

• Adds OrganizationEventType.ACCESS_DENIED to failed event detection alongside existing event types containing "fail".
• Bumps qovery-typescript-axios to 1.1.988 to expose the new ACCESS_DENIED constant.
• Adds test coverage for ACCESS_DENIED and POLICY_FAILED rendering as failed events.

^{Written for commit cd1c2d0. Summary will update on new commits.}